Deploy Release Package

Deploying a release package is the final stage of the release management process in Oracle Insurance Rules Workbench. Deployment is performed in the target environment without requiring logout from the Rules Workbench web application.

The target environment is selected from the Environment dropdown.

Environment roles (source or target) are defined during environment configuration
Environment Type Release Management Release Management Entry Environment

Source Environment

ON

True

Target Environment

ON

False

Prerequisites

  • The release package must have a status of ReadyToPromote in the originating environment.

  • Approval must be completed if the approval workflow is enabled.

  • Appropriate security privileges are required to approve and deploy release packages.

  • Deployment order must follow the sequence specified by the build manager:

    • When deploying across multiple environments, follow the sequence as defined.

    • When deploying multiple packages, deploy according to the defined order.

    • An error message is displayed if the deployment sequence is incorrect.

Steps to Approve and Deploy the Release Package

  1. Switch to the Deployment Environment

    1. Select the target environment from the Environment dropdown (top-right corner).

    2. Environment switching does not require logging out of the application.

  2. Locate the Release Package

    1. In the Navigation Explorer, go to Release Management | Release Packages folder.

    2. Identify the release package with a status of ReadyToPromote.

  3. Approve the Release Package

    1. Select the release package.

    2. In the Configuration Panel, click Promote.

    3. The status updates from ReadyToPromote to Promoted and the progress indicator advances.

    4. The Deploy button becomes active.

  4. Deploy the Release Package

    1. With the package status as Promoted, click Deploy.

    2. The status changes from Promoted to Deployed and the progress advances to the final step.

    3. The package now appears under the Deployed node in the deployment environment.

    4. In the originating environment, the package remains in ReadyToPromote until deployment is completed in all designated environments.

    Note: Deployment Rollback is planned for a future release and is not currently available in Rules Workbench.

 

Deployment Rollback

Release packages deployed to target environments can be "rolled back" if needed, reversing the deployment. This ability is useful if, for example, an error with the release package is found, or if the package is deployed to the incorrect environment. Release packages cannot be rolled back from source environments.

Just as the Rules workbench enforces the order in which release packages are deployed, it will enforce the order in which release packages are rolled back. Release packages must be rolled back in the reverse order that they were deployed. An error message will display if a user attempts to roll back a release package in an incorrect order.

Since rollbacks are not allowed in a source environment, detached migrations cannot be rolled back. However, a release package created from a detached migration can be rolled back if it has been deployed to other environments.

To rollback a release package:

  1. In a target environment, navigate to the Release Management folder.

  2. Open the Release Packages folder.

  3. Open the Deployed folder.

  4. Click on the release package and select Rollback.

  5. Clicking the Rollback option displays a message stating, 'Release package rollback successfully'. The release package will be removed from the Deployed folder and re-added to the Promoted folder.